home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
maximus
/
flst105p.zip
/
FASTLST.DOC
< prev
next >
Wrap
Text File
|
1992-04-28
|
22KB
|
722 lines
******************************************************************************
* *
* *
* ******* ** **** ****** **** **** ****** *
* ** * **** ** ** * ** * ** ** ** * ** * *
* ** * ** ** ** ** ** ** ** *
* **** ** ** **** ** ** **** ** *
* ** * ****** ** ** ** * ** ** *
* ** ** ** ** ** ** ** ** ** ** ** *
* **** ** ** **** **** ******* **** **** *
* *
* *
* A new flexible and powerful nodelist compiler *
* *
* *
******************************************************************************
* *
* (C) Copyright 1992 by Alberto Pasquale *
* *
* A L L R I G H T S R E S E R V E D *
* *
******************************************************************************
* *
* FastLst is NOT free-software, it is distributed under the ShareWare *
* concept ! If you regularly use it, you should register for US$25 or *
* LIT30.000. The registration key removes the initial 10s pause. *
* See REGISTER.FRM for more details on how to register your copy. *
* *
******************************************************************************
* *
* How to contact the author: Alberto Pasquale of 2:332/504@fidonet.org *
* Viale Verdi 106 *
* 41100 Modena *
* Italy *
* *
******************************************************************************
FastLst ver 1.05 User Manual
DISCLAIMER
There is absolutely no warranty of any kind on this product.
The user of this program bears all risk as to its quality and
performance.
LICENSE
FastLst
Copyright 1992 by Alberto Pasquale, Modena, Italy
All rights reserved. Commercial distribution and/or use
prohibited without written permission of the author.
You may copy and distribute verbatim copies of the original
distribution archive of FastLst, providing you don't charge
any fee exceeding your actual costs.
If you regularly use FastLst, you should register your copy
(See Register.FRM).
Files in the original archive:
FastLst.Exe The executable program (Dos Version Only)
FastLstP.Exe The executable program (Os/2 Version Only)
FastLst.Cfg The sample configuration file
FastLst.Doc This documentation file
Readme.1st Important notes
Readme.Os2 (OS/2 version Only): notes by Pasquale Cantiello
Whatsnew.Txt Fixes and additions
Register.Frm The Registration Form
Pag. 1
Main characteristics:
- Compiles Version 6 and Version 7 format nodelists for use
with BinkleyTerm/Opus/Maximus.
- Full 4D (point) support both in Version 6 and Version 7.
- Integrated Merge-QuickSort routines to process Fidouser.Lst
and Version 7 indexes.
- With the command line switches -n and -d can be used on
nodelist/nodediff files that have different names from the
default NODELIST.nnn/NODEDIFF.nnn, thus making easy the
compilation of non-FidoNet nodelists.
- If more than one applicable nodediff file is present, all
of them are applied, in the correct order.
- The -e command line switch allows to apply nodediffs without
compiling the nodelist (for those who compile a local
segment but like to keep the complete nodelist up to date).
- MergeList option to substitute a nodelist segment with a
local up to date one.
- Very flexible modem type and cost setting/overriding for
use with Binkley's ModemTrans and Events.
- User Cost (Msg Fee) can be set different from Call Cost.
- 380KB of free memory are required, but all the available
conventional memory is used to speed-up the merge-sort process.
Pag. 2
OPERATION
After start-up FastLst will search for applicable NodeDiff
files, then it will process any necessary Merging of the
source nodelist (MergeList option), in the end it will compile
the main nodelist, adding any necessary segment (PvtList and
MyList options).
The source nodelist and nodediff must be in standard "St.
Louis" format, as described in FTS-0005. FastLst allows an
extension to the input nodelist format in order to support
true "4D" points.
Points are entered in the nodelist directly following their
bossnode. Each one starts with the POINT keyword, followed
by the point number. Example:
...
...
,504,Videl_3,Modena_I,Alberto_Pasquale,...
Point,1,SysOp_Point,Modena_I,Alberto_Pasquale,...
Point,2,CoSysOp_Point,Modena_I,Roberto_Zanasi,...
Point,3,...
The generated files are:
Version6 NODELIST.DAT, NODELIST.IDX
Version7 NODEX.DAT, NODEX.NDX
FidoUserLst FIDOUSER.LST
SysopNdx SYSOP.NDX (with Version7 Only)
FidoTxt NODELIST.TXT
FidoPrn NODELIST.PRN
Pag. 3
CONFIGURATION FILE
FastLst requires a configuration file (defaults to
FastLst.Cfg in the current directory). Before using FastLst
you should edit this file, following the comments in it.
We will now describe some of the most complex statements.
The names of the various parameters are NOT case sensitive.
Items in square brackets ([]) are optional.
Country <country>
Example: Country 39-
This is the string to be substituted with the Domestic
dialing prefix (see Dial statement): it must be your country's
international phone code. If the trailing '-' is omitted, it
will be present in the translated phone number after the
domestic prefix.
Nodes with a phone number that begins with this string
receive the default Domestic Cost (if no cost override is
present) (see Cost statement).
MaxBaud <baud>
Example: MaxBaud 2400
Baud rates in the nodelist that are higher than this value
are changed to it in output Nodelist.DAT/Nodex.DAT files.
Pag. 4
MergeList <[path]filename[.ext]>
If an extension is not present, the latest filename.nnn is
used, considering nnn as a 3 digit day of the year.
The specified nodelist segment is merged with the main one,
then the result is compiled.
This option is intended to merge YOUR zone, region, net or
hub nodelists to the world, zone or region nodelist.
This means that if you use the world nodelist and merge
your Region nodelist, the portion of world nodelist
corresponding to your region will be REPLACED by your
Region; then the resulting nodelist will be compiled.
This way you can use the world nodelist while having
your region segment always up to date.
ATTENTION: using the MergeList option is very different
from including your segment of nodelist with "mylist",
because mylist "appends" to your zone the specified
file, so that you have the new nodes that were not
present in the main nodelist, but you DON'T have the
modified entries updated (mylist does NOT substitute or
overlay the dupes, it only appends the fragment to your
zone).
Using Version 6 format, the changed entries in segments
appended by MyList will not be active.
Instead with Version 7 the appended segment entries are
put in the indexes in the place of their counterpart in
the previously compiled nodelist.
If you specify more than one MergeList files, each file
is merged with the preceding one: let's suppose you have
MergeList Zone.002
MergeList Region.033
Mergelist Net.332
Mergelist Hub.500
Hub.500 and Net.332 are merged into net.999, then net.999
is merged with Region.033 into region.999, then
region.999 is merged with Zone.002 into zone.999, in the
end zone.999 is merged with nodelist.ddd into
nodelist.999.
All .999 files except for the last are automatically
erased after use. The last .999 file (usually
nodelist.999) is compiled and NOT deleted.
I am HC, so I use:
MergeList Region.033
MergeList Hub.500
WARNING: The MergeList option ONLY works with YOUR
segments of nodelist. If you merge a Hub segment, it
is searched for in YOUR zone and net. If you have
configured FastLst for a point system using your
fakenet in the "Address" verb, then you CANNOT merge your
hub segment, since the fakenet seems to be your net.
Pag. 5
However you can use your 4D address in the "Address"
verb of the configuration file, so that you have no
problems in merging your hub segment, if you wish to do
that.
MyList <[path]filename[.ext]>
To add a local nodelist segment to the compilation. It is
added after your Zone segment.
If an extension is not present, the latest filename.nnn is
used, considering nnn as a 3 digit day of the year.
PvtList <[path]filename[.ext]>
As MyList, but there is no output to nodelist.txt/prn.
Include <[path]filename.ext>
In your configuration file you can include other
configuration files: as an example you can put all of your
Password statements in a separate file and include it.
The inclusion process can be nested, so that you can use the
"Include" statement in included files too.
TypeDef <flag> <type>
Case not significant in <flag>.
Examples:
TypeDef HST 1 ; set bit 0 of type if HST flag present
TypeDef PEP 2 ; set bit 1 of type if PEP flag present
TypeDef V32 4 ; set bit 2 of type if V32 flag present
TypeDef V32B 8 ; set bit 3 of type if V32B flag present
A V32B entry will have both bit 3 and 2 set since it
contains V32B as well as V32 as substrings in the FLAG
portion of the entry.
If you use BinkleyTerm with a HST+V32 modem you will use:
ModemTrans 1 <HSTdialstring>
ModemTrans 4 <V32dialstring>
Since Binkley uses the first modemtrans that has at
least one bit in common with the modem type, it will
use ModemTrans 1 for HST and HST+V32(B) modems (types 1
and 1+4=5 (1+4+8=13)) and ModemTrans 2 for V32, V32B
and V32+PEP.
Pag. 6
If you have a USR HST+V32B you will use:
ModemTrans 8 <V32Bdialstring>
ModemTrans 1 <HSTdialstring>
ModemTrans 4 <V32dialstring>
This way you will call in V32B the entries that have
the V32B flag, in HST those ones that don't have the
V32B but have the HST, in V32 those ones that have
neither the V32B nor the HST but do have the V32.
TypeCost <type> <cost>
Examples:
If you have two lines, one with PEP and one with HST
DUAL STANDARD (HST+V32), then you could organize your
system so that the PEP will call only PEP nodes and the
HST/DS will call all nodes that cannot be connected in PEP.
The Cost parameter could help you.
Let's suppose you have defined:
TypeDef HST 1
TypeDef PEP 2
TypeDef V32 4
You should then use:
TypeCost 1 100 ; cost 100 for HST
TypeCost 2 50 ; cost 50 for PEP
TypeCost 4 100 ; cost 100 for V32
TypeCost 5 100 ; cost 100 for HST+V32
TypeCost 6 50 ; cost 100 for PEP+V32
Of course any V32B flag would be processed as a V32 one.
If you configure your events so that the PEP line calls nodes
with a cost <= 50 and the HST/V32 line calls nodes with a
cost > 50 you have done it !
Dial [<domestic>][<international>]
Example: Dial 0 00
39-59-58 /-010 ; Special Case
39-59- ; Local Dialing Area
End
The 'Dial' statement begins a dial table, which is ended by an
'End' statement.
It can take two arguments that specify the default prefix/suffix
to be prepended/appended to domestic and international phone
numbers (after removing the "Country" string from the
domestic numbers).
Pag. 7
Subsequent entries after the 'Dial' statement are used to
specify the prefix/suffix to be prepended/appended to telephone
numbers that begin with the string on the left (that is
removed).
The first matching entry is used; if no entry apply, the
defaults are used.
All the prefix/suffix specifications take the form:
[<prefix>][/[<suffix>]]
So that you can use:
<search_string> ; to remove <search_string> from the
; beginning of the number.
<search_string> / ; Same as above.
<search_string> <prefix> ; to replace <search_string> with
; <prefix>
<search_string> <prefix>/ ; Same as above.
<search_string> /<suffix> ; to remove <search_string> and
; append <suffix>
<search_string> <prefix>/<suffix> ; to replace
; <search_string> with <prefix> and
; append <suffix>
Also the two arguments of the heading Dial statement take the
described forms, but if you want to specify an international
prefix/suffix while leaving empty the domestic one, then you
MUST use a slash '/' as the domestic argument.
Pag. 8
COMMAND LINE PARAMETERS
-h or -? for help
-n<nodelist>
Compile <nodelist>.nnn instead of NODELIST.nnn
-d<nodediff>
Apply <nodediff>.nnn instead of NODEDIFF.nnn
-c<config>
Use <config> configuration file instead of FASTLST.CFG
-l<logname>
Log activity to <logname> file
-g<mergelist>
Merge main nodelist with <mergelist>
-m<mylist>
Use <mylist> as an additional nodelist. If the main
nodelist is the complete one, <mylist> is compiled just
after your zone segment.
-p<pvtlist>
Use <pvtlist> as an additional private nodelist.
This works the same as -m<mylist>, but there is no
output to nodelist.txt/prn.
-b<baud>
Use <baud> in place of the one set in the config file.
-e
Apply nodediffs only (don't compile nodelist)
ERRORLEVELS
0 Normal termination
1 Help requested
2 Open error
3 Can't find nodelist file
4 Disk Full
5 Can't find config file
6 Configuration error
7 Out of memory
8 Merge error
Pag. 9
MISCELLANEOUS INFO
In the case of SysOps of more than one system, the one to be
put in the SysOp Name List (Fidouser.lst and Sysop.ndx) is
chosen by using the following priority sequence (from highest
priority to lowest):
- Found in the latest included nodelist segment (w my/pvtList)
- Not redirected (fully active)
- High Speed Modem
- In your zone
- Crash Mail capable
- Not a coordinator
- NET number between 100 and 9999
- Not Mail Only
Redirected systems (Unpublished phone number, on HOLD) are
given the phone number, baud rate, modem type, call cost and
flags of the node they are redirected to, the Board name is
prepended with '-R-'.
A node is redirected to its coordinator, a point is
redirected to its boss (or to its boss' coordinator if the
boss is redirected).
If you have a session password with the system to be redirected
or with the system it should be redirected to, no redirection
is done in order to prevent password-mismatch errors in the
case the Unpublished/Hold System calls you.
These non-redirected systems take an EMPTY phone number string,
so that your mailer does not send unwanted strings to your modem
attempting to call these systems, should something appear in your
outbound addressed to them.
Pay attention: if you want to directly call these
null_phone-systems or their coordinators, you have to give
them a phone number using the "Phone <address> <number>"
statement in the configuration file.
The cost for a system is determined in the following way:
- The phone number determines the default to be used
(domestic or international).
- The entries in the "cost/end" statement can modify defaults
if a match is found with the phone number.
- The TypeCost statement can override the Cost in relation
to modem type.
- The "Cost <address>" statement can override the cost
established by the preceding statements.
In the case of Phone and Type overrides, the number and modem
type used for cost determination are the new ones.
The Modem Type for a system is determined in the following
way:
- Nodelist flags (in relation to "TypeDef" statements).
- Type Mask (optionally set by the "Cost/End" statement if
a phone number match occurs).
- "Type <address>" statement.
Pag. 10
The message fee (user cost) is especially useful when set to
0, so that you do not have to manually give credits to all of
your users.
If you use the following UCost table, then all nodelist
entries will have User_Cost = 0, thus allowing BBS users to
enter netmail messages even if they have no credits:
ucost 0 0
end
Pag. 11
